Use default charset (server side) instead of hard-coded ISO-8895-1 #14
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Use default charset (server side) instead of hard-coded ISO-8895-1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use default charset (server side) instead of hard-coded ISO-8895-1
more details are in the Ticket: https://support.fusioncharts.com/helpdesk/tickets/544292
Main issue is Export charts with Japanese chars , the charectes are garbled
fusionexport-java-client while preparing the multipart payload in class HttpConnectionManager.addReqParam(String key, String value) which calls http4 Mime library builder MultipartEntityBuilder.addTextBody(key, value) which adds request param with content type DEFAULT_TEXT that has encoding ISO_8859_1 because of that the payload is all garbled when sent to fusion-server
Before
After